TRG Suggestion - Application Testing - Test Automation with Cucumber #1148
Conversation
Suggestion for a Tractus-X Release Guideline for test automation using the Cucumber framework.
There was a problem hiding this comment.
I have a general issue with this TRG. I see basically two separate issues which should be covered:
- The general requirement towards automated testing which would have a normative meaning-> That is not covered at all
- A recommendation of how automated tests should be done -> Not normative
The current approach is "Use Gherkin to do automated tests". That is not a TRG. I strongly object that this gets active.
|
|
||
| ## Compliance | ||
|
|
||
| This TRG serves as a recommendation. While product teams may adopt other frameworks or tools to implement their test automation, the use of Cucumber with test cases written in Gherkin syntax as a basis is encouraged as a suggested best practice at the integration test level. |
There was a problem hiding this comment.
| This TRG serves as a recommendation. While product teams may adopt other frameworks or tools to implement their test automation, the use of Cucumber with test cases written in Gherkin syntax as a basis is encouraged as a suggested best practice at the integration test level. | |
| the use of Cucumber with test cases written in Gherkin syntax as a basis is encouraged as a suggested best practice at the integration test level. |
this should not be the case.
the way tests are expressed should be a choice made by the product team based on what's the desired outcome.
Certain products could benefit from the gherkin syntax because non-technical people could read it and understand how the product is working (please note that this is not always the case anyway :) ), but it would also be fair to point out that cucumber tests are harder to maintain because the additional ".feature to code" layer needed, and not all the teams want to deal with this burden.
Tractus-X Release Guideline (TRG) for test automation using the Cucumber framework. The guideline would initially not be a requirement but a suggestion, as other methods for test automation can be used by product teams.
Description
Providing a Tractus-X Release Guideline (TRG) for Test Automation with the widely-used Cucumber framework for behavior-driven test development, using the simple Gherkin syntax to describe test cases. This is suggested in order to provide product teams with a best-practice to start with or improve the basis for their test automation.
Focus for its use will be on API tests at the integration test level (end-to-end), as well as UI tests for products where this is applicable.
Test automation with Unit Tests at lower test levels are out of scope of this TRG, as those are already covered elsewhere as a standard practice.
Created by issue:
eclipse-tractusx/sig-release#969
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: